Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 653c96c4131a0135ba5a2ea2def4aba0866228131bffb57fbcb604af1760c176

Tx prefix hash: 2c6e98b777303fe63d191832e1e6d3d2bdea39d629fd840f99fe23e989606640
Tx public key: 3eec619e2b563f7fd8559042ca97428ea19d451bf71950508f42e425020ca4dc
Timestamp: 1720891388 Timestamp [UCT]: 2024-07-13 17:23:08 Age [y:d:h:m:s]: 00:249:13:31:30
Block: 1064960 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178286 RingCT/type: yes/0
Extra: 013eec619e2b563f7fd8559042ca97428ea19d451bf71950508f42e425020ca4dc02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1cce91039c1f44e4e97fbf6268e3439982bedb7540917c2c3aa3b3456765a060 0.600000000000 1535501 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": 1064970, "vin": [ { "gen": { "height": 1064960 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1cce91039c1f44e4e97fbf6268e3439982bedb7540917c2c3aa3b3456765a060" } } ], "extra": [ 1, 62, 236, 97, 158, 43, 86, 63, 127, 216, 85, 144, 66, 202, 151, 66, 142, 161, 157, 69, 27, 247, 25, 80, 80, 143, 66, 228, 37, 2, 12, 164, 220, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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