Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c9ab5ea93133c3cfe0c81952ee29ea2cb8b6b868934644c16f36d4fe6af0d57

Tx prefix hash: 52b2cff05ca9ef6523111a31ad72fe2f843279b26a9836c09620130adb9159ce
Tx public key: 3d9e96d852dd33eec2cdf3484e1c77d2f23da129c050e81f28a91cd314d09907
Timestamp: 1747498232 Timestamp [UCT]: 2025-05-17 16:10:32 Age [y:d:h:m:s]: 00:187:22:24:20
Block: 1284996 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132012 RingCT/type: yes/0
Extra: 013d9e96d852dd33eec2cdf3484e1c77d2f23da129c050e81f28a91cd314d099070211000000051f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 037b6eb243c1f856333d09c3e822eb8f96bc30d165995a1abbf4e77543a4553c 0.600000000000 1772459 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": 1285006, "vin": [ { "gen": { "height": 1284996 } } ], "vout": [ { "amount": 600000000, "target": { "key": "037b6eb243c1f856333d09c3e822eb8f96bc30d165995a1abbf4e77543a4553c" } } ], "extra": [ 1, 61, 158, 150, 216, 82, 221, 51, 238, 194, 205, 243, 72, 78, 28, 119, 210, 242, 61, 161, 41, 192, 80, 232, 31, 40, 169, 28, 211, 20, 208, 153, 7, 2, 17, 0, 0, 0, 5, 31, 144, 81, 122, 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