Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4da655e80e8ede337ccc86a8b33ceede7a843f8c15d9cc72b2e72fa0c2bd1a72

Tx prefix hash: 42b316aca732b1596c4d4021dc4b4fe99eac5e425e5af5018a0d94d95c1a3b97
Tx public key: b6b7304ac6f64654dde33ef1307e2ec0f2be963907b155e948d495cfd8d7519f
Timestamp: 1720613420 Timestamp [UCT]: 2024-07-10 12:10:20 Age [y:d:h:m:s]: 00:164:17:43:56
Block: 1062647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117902 RingCT/type: yes/0
Extra: 01b6b7304ac6f64654dde33ef1307e2ec0f2be963907b155e948d495cfd8d7519f021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e802075ffbeebf46acac58eb8a1b3596192bc5ff5579c4c506bf90581e89fc18 0.600000000000 1533152 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": 1062657, "vin": [ { "gen": { "height": 1062647 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e802075ffbeebf46acac58eb8a1b3596192bc5ff5579c4c506bf90581e89fc18" } } ], "extra": [ 1, 182, 183, 48, 74, 198, 246, 70, 84, 221, 227, 62, 241, 48, 126, 46, 192, 242, 190, 150, 57, 7, 177, 85, 233, 72, 212, 149, 207, 216, 215, 81, 159, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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