Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a238518cb43f0b4181edfcf43c60e76e7743c1faa11c3c75e433f4615cfdd7b2

Tx prefix hash: 3d6873803147b0ac2e4bdaad8872f9dffd1555b033a5f4fe41d896ed3a38fd11
Tx public key: d9afb11a716cafd9ec09d401fc97eea80d5566e9eb642588c57ae52ec6066c41
Timestamp: 1582901226 Timestamp [UCT]: 2020-02-28 14:47:06 Age [y:d:h:m:s]: 04:304:02:05:58
Block: 73495 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1110917 RingCT/type: yes/0
Extra: 01d9afb11a716cafd9ec09d401fc97eea80d5566e9eb642588c57ae52ec6066c41021100000005026b59f3000000000000000000

1 output(s) for total of 350.333247780000 dcy

stealth address amount amount idx
00: 1d21d3c6c2cc65549f970ba890b6bff9236357f8d23e42c95e143691390e547b 350.333247780000 135590 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": 73505, "vin": [ { "gen": { "height": 73495 } } ], "vout": [ { "amount": 350333247780, "target": { "key": "1d21d3c6c2cc65549f970ba890b6bff9236357f8d23e42c95e143691390e547b" } } ], "extra": [ 1, 217, 175, 177, 26, 113, 108, 175, 217, 236, 9, 212, 1, 252, 151, 238, 168, 13, 85, 102, 233, 235, 100, 37, 136, 197, 122, 229, 46, 198, 6, 108, 65, 2, 17, 0, 0, 0, 5, 2, 107, 89, 243, 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