Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6308393dfd1d6df56b30d2b830d2ca7d4602eee93d72cbaac6a99dc4c1b9eb5

Tx prefix hash: e85fdfe83921e0eaa59ebcb8dd020adaea70e17b5ba1b6edfac4cea4f5a4ecc4
Tx public key: 8cd45fcf28394c0d3e3d4f412036491f75574a6d0c9fa76dfa1c9b255086f737
Timestamp: 1764022200 Timestamp [UCT]: 2025-11-24 22:10:00 Age [y:d:h:m:s]: 00:028:18:09:49
Block: 1419396 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20573 RingCT/type: yes/0
Extra: 018cd45fcf28394c0d3e3d4f412036491f75574a6d0c9fa76dfa1c9b255086f737021100000005d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f5b5ec032be56850c4a44288ab31651f8d5006e805c4c08ab90dfa0f68ccf87 0.600000000000 1907933 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": 1419406, "vin": [ { "gen": { "height": 1419396 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f5b5ec032be56850c4a44288ab31651f8d5006e805c4c08ab90dfa0f68ccf87" } } ], "extra": [ 1, 140, 212, 95, 207, 40, 57, 76, 13, 62, 61, 79, 65, 32, 54, 73, 31, 117, 87, 74, 109, 12, 159, 167, 109, 250, 28, 155, 37, 80, 134, 247, 55, 2, 17, 0, 0, 0, 5, 214, 225, 157, 124, 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