Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 709d69f65c9c0e08a36ab746b261e01a29fad75366470cdcecfc068cd51808e0

Tx prefix hash: 0eb7fe3c775ec9ef422939a1bed3192eee16a6f0488d6d19b1a8282710a8f5d3
Tx public key: 4d0ad5a0e317685240b60a3a29372cf988cbe955e6a54c13eac44ba20288c8b6
Timestamp: 1730984193 Timestamp [UCT]: 2024-11-07 12:56:33 Age [y:d:h:m:s]: 00:016:19:15:46
Block: 1148536 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12022 RingCT/type: yes/0
Extra: 014d0ad5a0e317685240b60a3a29372cf988cbe955e6a54c13eac44ba20288c8b60211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0e73f7fe1730b98b5a0bcd33d8c99205dbf6265278caa75bcf22dec95c8a959 0.600000000000 1633407 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": 1148546, "vin": [ { "gen": { "height": 1148536 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0e73f7fe1730b98b5a0bcd33d8c99205dbf6265278caa75bcf22dec95c8a959" } } ], "extra": [ 1, 77, 10, 213, 160, 227, 23, 104, 82, 64, 182, 10, 58, 41, 55, 44, 249, 136, 203, 233, 85, 230, 165, 76, 19, 234, 196, 75, 162, 2, 136, 200, 182, 2, 17, 0, 0, 0, 1, 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