Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6102a75067deb962d8cf42c4b396addadfdcfce0a9c2f32786c68072ab00456c

Tx prefix hash: 68a2e074eecc08fc18f90566191a21337d33de20c356d2b54a0f8f4d1c2ef532
Tx public key: 35827cdc04373b56f23cf1dafb4defd68ab7d9b741b7fa1faa35b76dc8f76cfe
Timestamp: 1705283116 Timestamp [UCT]: 2024-01-15 01:45:16 Age [y:d:h:m:s]: 01:087:02:00:30
Block: 935516 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323357 RingCT/type: yes/0
Extra: 0135827cdc04373b56f23cf1dafb4defd68ab7d9b741b7fa1faa35b76dc8f76cfe02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2faae61977b7f04d9ff99b295ac750177c6ac18ebecdc9243a9175755b58200 0.600000000000 1393532 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": 935526, "vin": [ { "gen": { "height": 935516 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2faae61977b7f04d9ff99b295ac750177c6ac18ebecdc9243a9175755b58200" } } ], "extra": [ 1, 53, 130, 124, 220, 4, 55, 59, 86, 242, 60, 241, 218, 251, 77, 239, 214, 138, 183, 217, 183, 65, 183, 250, 31, 170, 53, 183, 109, 200, 247, 108, 254, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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