Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 704b135d3bdadb104f5bdddb73d1e66774873fd96f32165796e34534e1b18c46

Tx prefix hash: 551fa080cd72a79a611009aa7dd5fd2fa4bb2a88da762bc6d990a99a0fd1a37a
Tx public key: a26216d40381c3db87999ceca492b5d46c7c845ddba37f76e5f32e81b7b024e1
Timestamp: 1724840130 Timestamp [UCT]: 2024-08-28 10:15:30 Age [y:d:h:m:s]: 00:221:10:24:49
Block: 1097679 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158106 RingCT/type: yes/0
Extra: 01a26216d40381c3db87999ceca492b5d46c7c845ddba37f76e5f32e81b7b024e102110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f247e42612b27c3e90b4602ef80c45176e2a7bf0326fc3d2c604e84bc00b3ad3 0.600000000000 1573128 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": 1097689, "vin": [ { "gen": { "height": 1097679 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f247e42612b27c3e90b4602ef80c45176e2a7bf0326fc3d2c604e84bc00b3ad3" } } ], "extra": [ 1, 162, 98, 22, 212, 3, 129, 195, 219, 135, 153, 156, 236, 164, 146, 181, 212, 108, 124, 132, 93, 219, 163, 127, 118, 229, 243, 46, 129, 183, 176, 36, 225, 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