Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70b4fa84baa35831496b29bb3f5038b097d7883b1da377579a9b9aeb68f60765

Tx prefix hash: b25affa73a91043e094990c719ffb8899fd454bfaca5d47974b28f12d059e194
Tx public key: 4273e9a40f223da06dcb7af4e314139249caefbc3d381a53cb3c12f86fb1baf9
Timestamp: 1736938930 Timestamp [UCT]: 2025-01-15 11:02:10 Age [y:d:h:m:s]: 00:153:20:15:44
Block: 1197835 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109661 RingCT/type: yes/0
Extra: 014273e9a40f223da06dcb7af4e314139249caefbc3d381a53cb3c12f86fb1baf902110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd0b68529898c351fd6126fcaea38a3a95e4eb2d7cc0909f4245957537c7928b 0.600000000000 1684452 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": 1197845, "vin": [ { "gen": { "height": 1197835 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd0b68529898c351fd6126fcaea38a3a95e4eb2d7cc0909f4245957537c7928b" } } ], "extra": [ 1, 66, 115, 233, 164, 15, 34, 61, 160, 109, 203, 122, 244, 227, 20, 19, 146, 73, 202, 239, 188, 61, 56, 26, 83, 203, 60, 18, 248, 111, 177, 186, 249, 2, 17, 0, 0, 0, 10, 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