Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7150c82b9f10867c7e4e8401a6d395c0fecb8b22ae938c5341745ded547263dd

Tx prefix hash: ce4fa6a2671b7e7346f1c9af1303fc332b3316a1cd289be594e5c373429293da
Tx public key: cd98c8bb2ca15d5468afa77c0f2aafcdf08ca4b855e2e8d9ba50a02f9c41ec53
Timestamp: 1708200559 Timestamp [UCT]: 2024-02-17 20:09:19 Age [y:d:h:m:s]: 01:263:21:57:39
Block: 959729 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 447371 RingCT/type: yes/0
Extra: 01cd98c8bb2ca15d5468afa77c0f2aafcdf08ca4b855e2e8d9ba50a02f9c41ec5302110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 013821b83d136a3b028e36f03a1e10defe17dccf9acb446bd96aeb911d1c1e9f 0.600000000000 1419282 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": 959739, "vin": [ { "gen": { "height": 959729 } } ], "vout": [ { "amount": 600000000, "target": { "key": "013821b83d136a3b028e36f03a1e10defe17dccf9acb446bd96aeb911d1c1e9f" } } ], "extra": [ 1, 205, 152, 200, 187, 44, 161, 93, 84, 104, 175, 167, 124, 15, 42, 175, 205, 240, 140, 164, 184, 85, 226, 232, 217, 186, 80, 160, 47, 156, 65, 236, 83, 2, 17, 0, 0, 0, 1, 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