Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e869d439d3a173876966d0517b4a0328b41b37c2c6f68ab2c572a3ded03a23d

Tx prefix hash: e249bc2df48637b212be096eededfc94756f2e157287af8ae8153f52caa57f35
Tx public key: 0d181d163401e3e62bbe0cd825bc6c76ec662c57dc11201cfced7d824029f4c0
Timestamp: 1728240880 Timestamp [UCT]: 2024-10-06 18:54:40 Age [y:d:h:m:s]: 01:033:19:03:45
Block: 1125873 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282540 RingCT/type: yes/0
Extra: 010d181d163401e3e62bbe0cd825bc6c76ec662c57dc11201cfced7d824029f4c002110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9c20f57e6bf1dc4b04c9287fe197f03d5f06a396ce5f45052fff78b279f39f9 0.600000000000 1608644 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": 1125883, "vin": [ { "gen": { "height": 1125873 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9c20f57e6bf1dc4b04c9287fe197f03d5f06a396ce5f45052fff78b279f39f9" } } ], "extra": [ 1, 13, 24, 29, 22, 52, 1, 227, 230, 43, 190, 12, 216, 37, 188, 108, 118, 236, 102, 44, 87, 220, 17, 32, 28, 252, 237, 125, 130, 64, 41, 244, 192, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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