Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2c60f45b69c97029bafc02b7196fc62bff2e5a7653a9abb86d2c7918dd9a5db

Tx prefix hash: 351a840ffab019dc96fd2a99dee27f08e4303099900e702ad15768d0c21057ce
Tx public key: 658e69ead9d952aa34d6ff96557a38a36f16931f5fd14d593c40769a2a33184e
Timestamp: 1711917767 Timestamp [UCT]: 2024-03-31 20:42:47 Age [y:d:h:m:s]: 01:257:07:13:31
Block: 990564 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 442596 RingCT/type: yes/0
Extra: 01658e69ead9d952aa34d6ff96557a38a36f16931f5fd14d593c40769a2a33184e0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7e8452503a0481e79aa96af2012b7312fc3183ec27f83ef6078da49ec3ed9ce 0.600000000000 1450886 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": 990574, "vin": [ { "gen": { "height": 990564 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7e8452503a0481e79aa96af2012b7312fc3183ec27f83ef6078da49ec3ed9ce" } } ], "extra": [ 1, 101, 142, 105, 234, 217, 217, 82, 170, 52, 214, 255, 150, 85, 122, 56, 163, 111, 22, 147, 31, 95, 209, 77, 89, 60, 64, 118, 154, 42, 51, 24, 78, 2, 17, 0, 0, 0, 3, 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