Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7f261bbf02a8689210db08d191a8c5481786da94d9b9a991218c052b1fa9505

Tx prefix hash: 478094258e3406e9dec6ef81fb100d50439f55cd2360463552c5ec50a811aa14
Tx public key: dd3a26e7558997dc9220c4bcda47bbe6913a10b8c6735b4ce994ec6a85db678a
Timestamp: 1630044195 Timestamp [UCT]: 2021-08-27 06:03:15 Age [y:d:h:m:s]: 03:258:21:25:52
Block: 321646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 959384 RingCT/type: yes/0
Extra: 01dd3a26e7558997dc9220c4bcda47bbe6913a10b8c6735b4ce994ec6a85db678a02110000001ccd14b6bf000000000000000000

1 output(s) for total of 52.753798866000 dcy

stealth address amount amount idx
00: b7d282dbbcd88388a9b1a3356269927f254e02ff2927bfda0ca1315c38d0b14d 52.753798866000 667647 of 0

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": 321656, "vin": [ { "gen": { "height": 321646 } } ], "vout": [ { "amount": 52753798866, "target": { "key": "b7d282dbbcd88388a9b1a3356269927f254e02ff2927bfda0ca1315c38d0b14d" } } ], "extra": [ 1, 221, 58, 38, 231, 85, 137, 151, 220, 146, 32, 196, 188, 218, 71, 187, 230, 145, 58, 16, 184, 198, 115, 91, 76, 233, 148, 236, 106, 133, 219, 103, 138, 2, 17, 0, 0, 0, 28, 205, 20, 182, 191, 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