Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98820354165094343958b1814aa9107f332763d126d1dbe025cd39e7a49911e7

Tx prefix hash: 50898307ee5b6a4305136cc30146c1858b1064ad8ae4aba7297cb0ab7fa6720b
Tx public key: 6065c777310d7ca0343efe5e44beafe7bdf4bc862c0fcbdf90b1287fb07a3a68
Timestamp: 1712926207 Timestamp [UCT]: 2024-04-12 12:50:07 Age [y:d:h:m:s]: 01:054:18:41:45
Block: 998892 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300162 RingCT/type: yes/0
Extra: 016065c777310d7ca0343efe5e44beafe7bdf4bc862c0fcbdf90b1287fb07a3a6802110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13e1290cb6e6c4600e1558917745f83219f1ae4e4bd5bd732a7b6b6d2a79305c 0.600000000000 1459364 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": 998902, "vin": [ { "gen": { "height": 998892 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13e1290cb6e6c4600e1558917745f83219f1ae4e4bd5bd732a7b6b6d2a79305c" } } ], "extra": [ 1, 96, 101, 199, 119, 49, 13, 124, 160, 52, 62, 254, 94, 68, 190, 175, 231, 189, 244, 188, 134, 44, 15, 203, 223, 144, 177, 40, 127, 176, 122, 58, 104, 2, 17, 0, 0, 0, 6, 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