Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef5ac8ebacf1c833fcd8e972f0ca212d5d6ae3d81fafd7d966bf101b5d1b2b08

Tx prefix hash: 0b51f9633e4cb5706436164e7091e9ef8495c225d3079e0c88eeb7d110c2c265
Tx public key: 8ca703ac609006729b54f011df28ed90cbac3356a8cb4fb99bea850d383363ae
Timestamp: 1762375212 Timestamp [UCT]: 2025-11-05 20:40:12 Age [y:d:h:m:s]: 00:059:19:53:21
Block: 1405738 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 42859 RingCT/type: yes/0
Extra: 018ca703ac609006729b54f011df28ed90cbac3356a8cb4fb99bea850d383363ae0211000000015dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf7d32577ee522fd6a7f4a1013944925a28ebc2e425903e38b235fc159bd1e3a 0.600000000000 1894119 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": 1405748, "vin": [ { "gen": { "height": 1405738 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf7d32577ee522fd6a7f4a1013944925a28ebc2e425903e38b235fc159bd1e3a" } } ], "extra": [ 1, 140, 167, 3, 172, 96, 144, 6, 114, 155, 84, 240, 17, 223, 40, 237, 144, 203, 172, 51, 86, 168, 203, 79, 185, 155, 234, 133, 13, 56, 51, 99, 174, 2, 17, 0, 0, 0, 1, 93, 251, 190, 42, 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