Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f3850453aec79a4b88d9d35034c0361b4d0bf25b3a2c8f78ec874b5b93ff95f

Tx prefix hash: b0dcbe453187427b7cc8ac6c115cb671e562ae4db34d7f2811655ebd01ccbf13
Tx public key: e0bffd81dbb795a0df51a5ab95f81a62a2650cdea03cf39d3097c2e493a5cf88
Timestamp: 1639013558 Timestamp [UCT]: 2021-12-09 01:32:38 Age [y:d:h:m:s]: 03:030:21:59:33
Block: 391453 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 801034 RingCT/type: yes/0
Extra: 01e0bffd81dbb795a0df51a5ab95f81a62a2650cdea03cf39d3097c2e493a5cf88021100000001e9564d6f000000000000000000

1 output(s) for total of 30.970917767000 dcy

stealth address amount amount idx
00: dce366d6c6d4f5f04b62e3097f082a222f04420c746cf48ce5ebc4deedf385c8 30.970917767000 787856 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": 391463, "vin": [ { "gen": { "height": 391453 } } ], "vout": [ { "amount": 30970917767, "target": { "key": "dce366d6c6d4f5f04b62e3097f082a222f04420c746cf48ce5ebc4deedf385c8" } } ], "extra": [ 1, 224, 191, 253, 129, 219, 183, 149, 160, 223, 81, 165, 171, 149, 248, 26, 98, 162, 101, 12, 222, 160, 60, 243, 157, 48, 151, 194, 228, 147, 165, 207, 136, 2, 17, 0, 0, 0, 1, 233, 86, 77, 111, 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