Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80174aed79d3b425a606fd8d1c3a7e369ca953ed6f85681c4f4afd89cdd9cc07

Tx prefix hash: 038e047f8729fcb85b51c9362d18851ac363b08ee70b2b9da7562df37375f951
Tx public key: 70139962fcd6a8bce96c1212e04a17d6451b6940aaedef8feef17458086f96ff
Timestamp: 1697994044 Timestamp [UCT]: 2023-10-22 17:00:44 Age [y:d:h:m:s]: 01:232:05:25:13
Block: 875316 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 427040 RingCT/type: yes/0
Extra: 0170139962fcd6a8bce96c1212e04a17d6451b6940aaedef8feef17458086f96ff02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.772173247000 dcy

stealth address amount amount idx
00: d06fa787958cfcd4d8ba08b1b5fb11849db04366edbb3a25b79859dc64bbd361 0.772173247000 1330568 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": 875326, "vin": [ { "gen": { "height": 875316 } } ], "vout": [ { "amount": 772173247, "target": { "key": "d06fa787958cfcd4d8ba08b1b5fb11849db04366edbb3a25b79859dc64bbd361" } } ], "extra": [ 1, 112, 19, 153, 98, 252, 214, 168, 188, 233, 108, 18, 18, 224, 74, 23, 214, 69, 27, 105, 64, 170, 237, 239, 143, 238, 241, 116, 88, 8, 111, 150, 255, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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