Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23f14cc09a049b6538ffd411100a0b082c023a78ec623148119b2843af51e59f

Tx prefix hash: fefdf2323521d641e767ebc8bbae2419596ac2963ebef9d3dc5c974ffe2e0002
Tx public key: 2922ebc710ae5c76ce7350e0285c5b5eae76a73d15a9486388c8c60f48c11b2d
Timestamp: 1726669146 Timestamp [UCT]: 2024-09-18 14:19:06 Age [y:d:h:m:s]: 00:113:14:30:12
Block: 1112841 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81238 RingCT/type: yes/0
Extra: 012922ebc710ae5c76ce7350e0285c5b5eae76a73d15a9486388c8c60f48c11b2d021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3cb425fed92ded57390bc3f0891655f63044137247e71d4b4d6a2f54bed7f116 0.600000000000 1592306 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": 1112851, "vin": [ { "gen": { "height": 1112841 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3cb425fed92ded57390bc3f0891655f63044137247e71d4b4d6a2f54bed7f116" } } ], "extra": [ 1, 41, 34, 235, 199, 16, 174, 92, 118, 206, 115, 80, 224, 40, 92, 91, 94, 174, 118, 167, 61, 21, 169, 72, 99, 136, 200, 198, 15, 72, 193, 27, 45, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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