Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7f7db860de00098b0c5906f34bb5a1640f7ec2fc4ba7cb930cd06b674aef81c

Tx prefix hash: 5ed3e01e7fb4f3b1c46f0d31d44d740478bdfc21ee75aed63d3d4e7a202b4bb4
Tx public key: e974aa7ae84cef4c9d98ed5af0dcdca00c971de6ff71761df64b392ddc6065cb
Timestamp: 1658962410 Timestamp [UCT]: 2022-07-27 22:53:30 Age [y:d:h:m:s]: 02:161:00:40:30
Block: 553143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 636494 RingCT/type: yes/0
Extra: 01e974aa7ae84cef4c9d98ed5af0dcdca00c971de6ff71761df64b392ddc6065cb02110000001165468698000000000000000000

1 output(s) for total of 9.020025142000 dcy

stealth address amount amount idx
00: 74de0e3b14e1140a25897b53183b452771aedcef84107710c6d65e1ec462f858 9.020025142000 984915 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": 553153, "vin": [ { "gen": { "height": 553143 } } ], "vout": [ { "amount": 9020025142, "target": { "key": "74de0e3b14e1140a25897b53183b452771aedcef84107710c6d65e1ec462f858" } } ], "extra": [ 1, 233, 116, 170, 122, 232, 76, 239, 76, 157, 152, 237, 90, 240, 220, 220, 160, 12, 151, 29, 230, 255, 113, 118, 29, 246, 75, 57, 45, 220, 96, 101, 203, 2, 17, 0, 0, 0, 17, 101, 70, 134, 152, 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