Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e58aa97d345ce2ab0ea00ace2e9d63f058e3664a816d49c7bdf5cfb50082638

Tx prefix hash: a2c9634a3149625b406990cd791535f38d9b3188fd41e10c68cf42b3f9a82e40
Tx public key: 72c2753728e4044af0ac8fb25e2aabfcf5277c33daa32b92601a9d0cee5128d9
Timestamp: 1731244615 Timestamp [UCT]: 2024-11-10 13:16:55 Age [y:d:h:m:s]: 00:141:01:23:30
Block: 1150686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100638 RingCT/type: yes/0
Extra: 0172c2753728e4044af0ac8fb25e2aabfcf5277c33daa32b92601a9d0cee5128d90211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ccba624e1a8820824d6bafc3af7906bccfbe1e453f6df52cda68f74c6da4b802 0.600000000000 1636063 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": 1150696, "vin": [ { "gen": { "height": 1150686 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ccba624e1a8820824d6bafc3af7906bccfbe1e453f6df52cda68f74c6da4b802" } } ], "extra": [ 1, 114, 194, 117, 55, 40, 228, 4, 74, 240, 172, 143, 178, 94, 42, 171, 252, 245, 39, 124, 51, 218, 163, 43, 146, 96, 26, 157, 12, 238, 81, 40, 217, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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