Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2fca4e50f7b6f1bb6c957f02a5caaf321e5e0b9d51160ce12db0a330a17f50ab

Tx prefix hash: 210b1c3e758807ae01745884de86afd4dd1ec9caedb886d5d5ae3243989fcd42
Tx public key: 86c01aae573eb0f0cc39fe22d170470752b2c6bd1fff8b2c27de42b113252c13
Timestamp: 1711762831 Timestamp [UCT]: 2024-03-30 01:40:31 Age [y:d:h:m:s]: 01:007:08:42:27
Block: 989283 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266211 RingCT/type: yes/0
Extra: 0186c01aae573eb0f0cc39fe22d170470752b2c6bd1fff8b2c27de42b113252c1302110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 020dbc1be78cd3b0c268619e9f234fe82db88edb405ef7899a17597051777fd3 0.600000000000 1449578 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": 989293, "vin": [ { "gen": { "height": 989283 } } ], "vout": [ { "amount": 600000000, "target": { "key": "020dbc1be78cd3b0c268619e9f234fe82db88edb405ef7899a17597051777fd3" } } ], "extra": [ 1, 134, 192, 26, 174, 87, 62, 176, 240, 204, 57, 254, 34, 209, 112, 71, 7, 82, 178, 198, 189, 31, 255, 139, 44, 39, 222, 66, 177, 19, 37, 44, 19, 2, 17, 0, 0, 0, 2, 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