Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f6618159145cb62c74dfa67efbbcde014830248908a958056d81926a1f85989

Tx prefix hash: 06dd7053976ac066d04c1eedfd1768ded0d38ea31b04b95b8585a7f0cd45c86b
Tx public key: fd33260552b1dc1360ddca975d1a12fdb6a8ad84b1f207891f4ed5aaa0e629f9
Timestamp: 1666234685 Timestamp [UCT]: 2022-10-20 02:58:05 Age [y:d:h:m:s]: 02:130:04:21:52
Block: 612850 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 614642 RingCT/type: yes/0
Extra: 01fd33260552b1dc1360ddca975d1a12fdb6a8ad84b1f207891f4ed5aaa0e629f902110000000975e3f0e9000000000000000000

1 output(s) for total of 5.719704403000 dcy

stealth address amount amount idx
00: 01e1959fd12219e00ac6ab0a6d77075a3b620575bcd3fb64d492b82d08752120 5.719704403000 1050091 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": 612860, "vin": [ { "gen": { "height": 612850 } } ], "vout": [ { "amount": 5719704403, "target": { "key": "01e1959fd12219e00ac6ab0a6d77075a3b620575bcd3fb64d492b82d08752120" } } ], "extra": [ 1, 253, 51, 38, 5, 82, 177, 220, 19, 96, 221, 202, 151, 93, 26, 18, 253, 182, 168, 173, 132, 177, 242, 7, 137, 31, 78, 213, 170, 160, 230, 41, 249, 2, 17, 0, 0, 0, 9, 117, 227, 240, 233, 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