Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47e4f1d87269eb482badf7304be9ee887b08f567733cac3bf4fe930d0a99e9f6

Tx prefix hash: 5a0e52ce186775c5416324de200f414534d73a6036274e775630f97514c964ba
Tx public key: 1f79acda147722c0fe0592a135645294f5d8ba0fdd576e2b6cd0b40668514a40
Timestamp: 1577801505 Timestamp [UCT]: 2019-12-31 14:11:45 Age [y:d:h:m:s]: 04:359:22:41:52
Block: 35829 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1146342 RingCT/type: yes/0
Extra: 011f79acda147722c0fe0592a135645294f5d8ba0fdd576e2b6cd0b40668514a4002110000000e8a2ee0d9000000000000000000

1 output(s) for total of 466.965185917000 dcy

stealth address amount amount idx
00: d115bdddc2ae80630747ed66dbf2533ee5806dc619602ceb88bea9c269aec1df 466.965185917000 60479 of 0

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": 35839, "vin": [ { "gen": { "height": 35829 } } ], "vout": [ { "amount": 466965185917, "target": { "key": "d115bdddc2ae80630747ed66dbf2533ee5806dc619602ceb88bea9c269aec1df" } } ], "extra": [ 1, 31, 121, 172, 218, 20, 119, 34, 192, 254, 5, 146, 161, 53, 100, 82, 148, 245, 216, 186, 15, 221, 87, 110, 43, 108, 208, 180, 6, 104, 81, 74, 64, 2, 17, 0, 0, 0, 14, 138, 46, 224, 217, 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