Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1bce8c331539f87bf0b324e53f6db19f81e561866a7f1b17e638776b2c89eb0e

Tx prefix hash: f370378f3c814beafa4e4f668cf4d8012277f3968edfc239ce7d66e31f79faa7
Tx public key: 5e4a01b2f72e3222172ccacfd5114e274f8df689ece65f1d86a5efad2f2a0816
Timestamp: 1763037151 Timestamp [UCT]: 2025-11-13 12:32:31 Age [y:d:h:m:s]: 00:056:08:16:01
Block: 1411233 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40346 RingCT/type: yes/0
Extra: 015e4a01b2f72e3222172ccacfd5114e274f8df689ece65f1d86a5efad2f2a0816021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 89b87e7912326af3535dceed65f09c73b5f42ae1e5c314c0c4347a26c7b6fec8 0.600000000000 1899692 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": 1411243, "vin": [ { "gen": { "height": 1411233 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89b87e7912326af3535dceed65f09c73b5f42ae1e5c314c0c4347a26c7b6fec8" } } ], "extra": [ 1, 94, 74, 1, 178, 247, 46, 50, 34, 23, 44, 202, 207, 213, 17, 78, 39, 79, 141, 246, 137, 236, 230, 95, 29, 134, 165, 239, 173, 47, 42, 8, 22, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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