Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 610537b234763620effd68dc1bb7c4891ffb0eaf82604c02005705c3b58fbeb6

Tx prefix hash: 2360a52264c108ea4d715c9b9f1d4cb92f992247a1f8f59b9105a0e29a1cb8c9
Tx public key: f9d624a2e564db2fb90bd53ce927919f48caf8f248ce93427a5cffb8d2fed6fb
Timestamp: 1745653344 Timestamp [UCT]: 2025-04-26 07:42:24 Age [y:d:h:m:s]: 00:214:06:41:53
Block: 1269720 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150871 RingCT/type: yes/0
Extra: 01f9d624a2e564db2fb90bd53ce927919f48caf8f248ce93427a5cffb8d2fed6fb02110000000adbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 871156c309f499c0ecce45c5dcc60ef88f0ddf9a5884139feda1baaf11103d62 0.600000000000 1756959 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": 1269730, "vin": [ { "gen": { "height": 1269720 } } ], "vout": [ { "amount": 600000000, "target": { "key": "871156c309f499c0ecce45c5dcc60ef88f0ddf9a5884139feda1baaf11103d62" } } ], "extra": [ 1, 249, 214, 36, 162, 229, 100, 219, 47, 185, 11, 213, 60, 233, 39, 145, 159, 72, 202, 248, 242, 72, 206, 147, 66, 122, 92, 255, 184, 210, 254, 214, 251, 2, 17, 0, 0, 0, 10, 219, 181, 113, 193, 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