Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a529a163d71d168ad485a529739b02e12a67578a78027787c2b9aad1a3d2f692

Tx prefix hash: 9170c387265f29c760f0c4418c5a578221e2536c2adfed23b3a2152817caef42
Tx public key: d6ab16872ef1e051b14dd0e90deccd65577db9e192b208c6e41d2c19c0e6ef9f
Timestamp: 1734030281 Timestamp [UCT]: 2024-12-12 19:04:41 Age [y:d:h:m:s]: 00:110:06:50:53
Block: 1173791 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78575 RingCT/type: yes/0
Extra: 01d6ab16872ef1e051b14dd0e90deccd65577db9e192b208c6e41d2c19c0e6ef9f021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d1462d75f3bb9d62abaa30f57d791649e3c00ef12fab34b391d2e4150b76e49 0.600000000000 1659854 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": 1173801, "vin": [ { "gen": { "height": 1173791 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d1462d75f3bb9d62abaa30f57d791649e3c00ef12fab34b391d2e4150b76e49" } } ], "extra": [ 1, 214, 171, 22, 135, 46, 241, 224, 81, 177, 77, 208, 233, 13, 236, 205, 101, 87, 125, 185, 225, 146, 178, 8, 198, 228, 29, 44, 25, 192, 230, 239, 159, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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