Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2f1429b1461573c99f9af707efb996ebfcb4ac8deb48d0b057b9cf7f889ab48

Tx prefix hash: 7223c61cfd9f00d5af5862996fd232cea7d0917f92fe64fb759d5e59dbbd7c78
Tx public key: 451fe6c47a2b6a8fd9fa223fe9f6053725a9cf5a3121b94a3c1a80a7725a2f17
Timestamp: 1737449357 Timestamp [UCT]: 2025-01-21 08:49:17 Age [y:d:h:m:s]: 00:300:17:26:23
Block: 1202027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212480 RingCT/type: yes/0
Extra: 01451fe6c47a2b6a8fd9fa223fe9f6053725a9cf5a3121b94a3c1a80a7725a2f170211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 271084509cbc2994c64591b7594c95c5393870cee18fe03063e774eaa7e68881 0.600000000000 1688686 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": 1202037, "vin": [ { "gen": { "height": 1202027 } } ], "vout": [ { "amount": 600000000, "target": { "key": "271084509cbc2994c64591b7594c95c5393870cee18fe03063e774eaa7e68881" } } ], "extra": [ 1, 69, 31, 230, 196, 122, 43, 106, 143, 217, 250, 34, 63, 233, 246, 5, 55, 37, 169, 207, 90, 49, 33, 185, 74, 60, 26, 128, 167, 114, 90, 47, 23, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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