Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 020cff0c0cbeb00320a74c629fd36d8d03d8d97d24378f7ca4f03b7eb6c038e6

Tx prefix hash: 39b63b7e4f192c0c9f3d380a2a68c73d907aed49c370cbe32f5974bb387e6605
Tx public key: 9dadef49cef6786eb9e59913f9b3361e560d5f32d7038bfca0f8c5b217561e3f
Timestamp: 1752849576 Timestamp [UCT]: 2025-07-18 14:39:36 Age [y:d:h:m:s]: 00:173:22:19:16
Block: 1328171 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123175 RingCT/type: yes/0
Extra: 019dadef49cef6786eb9e59913f9b3361e560d5f32d7038bfca0f8c5b217561e3f021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e4aae3d3fb8f7b69c1ad3eb74db2a4bf4cc442c18f06a64c389f989816f457e 0.600000000000 1815932 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": 1328181, "vin": [ { "gen": { "height": 1328171 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e4aae3d3fb8f7b69c1ad3eb74db2a4bf4cc442c18f06a64c389f989816f457e" } } ], "extra": [ 1, 157, 173, 239, 73, 206, 246, 120, 110, 185, 229, 153, 19, 249, 179, 54, 30, 86, 13, 95, 50, 215, 3, 139, 252, 160, 248, 197, 178, 23, 86, 30, 63, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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