Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 009d7aa260850db71232a32f1ea899c0571aa14b8881f676010e78d6dd147df6

Tx prefix hash: e95df9386ad3e38f4833818d160d27df89517cdc5d12b66ce6294856d4f94429
Tx public key: 7dfdca3cb5d4204a79cadc68ace068fdb9539835e54ead02c76a4dfbb24d8c33
Timestamp: 1720864445 Timestamp [UCT]: 2024-07-13 09:54:05 Age [y:d:h:m:s]: 00:275:06:26:43
Block: 1064743 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196650 RingCT/type: yes/0
Extra: 017dfdca3cb5d4204a79cadc68ace068fdb9539835e54ead02c76a4dfbb24d8c3302110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65a5f80e1b8d3a49e1229ccfc75256793e113a1cbd671f0a30ef71522b53852a 0.600000000000 1535278 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": 1064753, "vin": [ { "gen": { "height": 1064743 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65a5f80e1b8d3a49e1229ccfc75256793e113a1cbd671f0a30ef71522b53852a" } } ], "extra": [ 1, 125, 253, 202, 60, 181, 212, 32, 74, 121, 202, 220, 104, 172, 224, 104, 253, 185, 83, 152, 53, 229, 78, 173, 2, 199, 106, 77, 251, 178, 77, 140, 51, 2, 17, 0, 0, 0, 1, 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