Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 09af3263b95acaedcb5c3adf11364d77a104dbf1b171fa6712c19f5d16a7b37b

Tx prefix hash: 1d75f685705622f43b32e00f42544aeba85ac0cf113e5bc73b59f4bef51a847c
Tx public key: f7a168040acc561ef6d7cc4aa9dfffcd20a663f35cccae9e5626b10f1fdffab0
Timestamp: 1580476212 Timestamp [UCT]: 2020-01-31 13:10:12 Age [y:d:h:m:s]: 05:024:09:47:45
Block: 55712 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1169382 RingCT/type: yes/0
Extra: 01f7a168040acc561ef6d7cc4aa9dfffcd20a663f35cccae9e5626b10f1fdffab0021100000001ff58ae94000000000000000000

1 output(s) for total of 401.239648666000 dcy

stealth address amount amount idx
00: 5ac0c2cc3b85f302592ac0e8d89e4e6fb5f6c6be31f830b6462a3c3e3643f72a 401.239648666000 102813 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 55722, "vin": [ { "gen": { "height": 55712 } } ], "vout": [ { "amount": 401239648666, "target": { "key": "5ac0c2cc3b85f302592ac0e8d89e4e6fb5f6c6be31f830b6462a3c3e3643f72a" } } ], "extra": [ 1, 247, 161, 104, 4, 10, 204, 86, 30, 246, 215, 204, 74, 169, 223, 255, 205, 32, 166, 99, 243, 92, 204, 174, 158, 86, 38, 177, 15, 31, 223, 250, 176, 2, 17, 0, 0, 0, 1, 255, 88, 174, 148, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8