Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 792217d6f2390dd4824fe93e2d6494a6cb51cfb9152c0f37b75512481fafe1cd

Tx prefix hash: 5901dd4b4a49fc7ce485761349b1ca8f68b2934fd868bfae7affbb1fa70e085e
Tx public key: d7a2b67e223e7492d7195d837f8ca5721c17c0b578a7596d75d1c6010c6d2cec
Timestamp: 1709479839 Timestamp [UCT]: 2024-03-03 15:30:39 Age [y:d:h:m:s]: 01:109:05:35:11
Block: 970344 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338963 RingCT/type: yes/0
Extra: 01d7a2b67e223e7492d7195d837f8ca5721c17c0b578a7596d75d1c6010c6d2cec02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab33af45283e5947e951c4aaf988966bb8eace7a30c5ad443ab082f210fa424e 0.600000000000 1430195 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": 970354, "vin": [ { "gen": { "height": 970344 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab33af45283e5947e951c4aaf988966bb8eace7a30c5ad443ab082f210fa424e" } } ], "extra": [ 1, 215, 162, 182, 126, 34, 62, 116, 146, 215, 25, 93, 131, 127, 140, 165, 114, 28, 23, 192, 181, 120, 167, 89, 109, 117, 209, 198, 1, 12, 109, 44, 236, 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