Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d3ddf578b56f4608d10dd5b54c5a2a562bfdd60bcf78aba41341c316b3c63af

Tx prefix hash: deb2e87ca54b1f645410e084659754b0370a265d1922864a1e31e0056783e52f
Tx public key: 1b307f4fb7749b1d36936dfb07b7c11f574186c58a374ce5acd0e14ea3180011
Timestamp: 1743739641 Timestamp [UCT]: 2025-04-04 04:07:21 Age [y:d:h:m:s]: 00:231:11:49:04
Block: 1253870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163173 RingCT/type: yes/0
Extra: 011b307f4fb7749b1d36936dfb07b7c11f574186c58a374ce5acd0e14ea31800110211000000044060f6d2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f44aebd6ee7aac9b2fd22601d1f0b4fe6ebd09acc123016797de1792800ade62 0.600000000000 1740951 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": 1253880, "vin": [ { "gen": { "height": 1253870 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f44aebd6ee7aac9b2fd22601d1f0b4fe6ebd09acc123016797de1792800ade62" } } ], "extra": [ 1, 27, 48, 127, 79, 183, 116, 155, 29, 54, 147, 109, 251, 7, 183, 193, 31, 87, 65, 134, 197, 138, 55, 76, 229, 172, 208, 225, 78, 163, 24, 0, 17, 2, 17, 0, 0, 0, 4, 64, 96, 246, 210, 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