Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c84d47e65d55d5ced83c9000f9f91fc74f551ab206e918e54d6f49cff8d3c6c5

Tx prefix hash: bade52bc163bbd6691a5c5192dd3fe950ed61003f7c812040afb6be8fe021b66
Tx public key: f0c8e4c84b7fe98a8315839a299ea702e74f1bdc546266f3dcaa0aca12759ef9
Timestamp: 1734355070 Timestamp [UCT]: 2024-12-16 13:17:50 Age [y:d:h:m:s]: 00:093:09:32:51
Block: 1176482 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66533 RingCT/type: yes/0
Extra: 01f0c8e4c84b7fe98a8315839a299ea702e74f1bdc546266f3dcaa0aca12759ef9021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6427a461e1f9aa0979e2898cb09e7dc5302e896ed56e994fa581c4a8a4998f24 0.600000000000 1662815 of 15

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": 1176492, "vin": [ { "gen": { "height": 1176482 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6427a461e1f9aa0979e2898cb09e7dc5302e896ed56e994fa581c4a8a4998f24" } } ], "extra": [ 1, 240, 200, 228, 200, 75, 127, 233, 138, 131, 21, 131, 154, 41, 158, 167, 2, 231, 79, 27, 220, 84, 98, 102, 243, 220, 170, 10, 202, 18, 117, 158, 249, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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