Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7198be1e93fface1dab7a8aa48ffbc70c681a1e2d54e2700e7212f71262f4f9

Tx prefix hash: 34eeada3994bc8fc383882551aca8099a09708f1ba6982ea61c207a2ca92f802
Tx public key: fa42341f9640b9a6ec37d1a2dff2e6d42d0e203805ba3595c826c1c135d952d2
Timestamp: 1711764113 Timestamp [UCT]: 2024-03-30 02:01:53 Age [y:d:h:m:s]: 01:220:21:25:10
Block: 989291 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 416518 RingCT/type: yes/0
Extra: 01fa42341f9640b9a6ec37d1a2dff2e6d42d0e203805ba3595c826c1c135d952d20211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 394d76e1d5c09fe76609ac5ab6d727991be62779847df78eedcd64786d383ff2 0.600000000000 1449586 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": 989301, "vin": [ { "gen": { "height": 989291 } } ], "vout": [ { "amount": 600000000, "target": { "key": "394d76e1d5c09fe76609ac5ab6d727991be62779847df78eedcd64786d383ff2" } } ], "extra": [ 1, 250, 66, 52, 31, 150, 64, 185, 166, 236, 55, 209, 162, 223, 242, 230, 212, 45, 14, 32, 56, 5, 186, 53, 149, 200, 38, 193, 193, 53, 217, 82, 210, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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