Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19b6bb4a7fac2ad521de4176b23bdb2c8501ebe663cd09b724fd8cd074f62122

Tx prefix hash: 42aba9d20622ad370a262c323e8e3ac7676a315b0d346378ac3a553e7af5a991
Tx public key: 6ee8a716cd07533cbc3ccc67d30e585a348cf54c7f395bd83c8aa0c5a2e65f06
Timestamp: 1765400800 Timestamp [UCT]: 2025-12-10 21:06:40 Age [y:d:h:m:s]: 00:021:03:24:09
Block: 1430816 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 15138 RingCT/type: yes/0
Extra: 016ee8a716cd07533cbc3ccc67d30e585a348cf54c7f395bd83c8aa0c5a2e65f0602110000000370609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3a79ab14072249c340b04d6ac9b15fbc14339ce1720bba2e75d7b6f8f712440 0.600000000000 1919569 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": 1430826, "vin": [ { "gen": { "height": 1430816 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3a79ab14072249c340b04d6ac9b15fbc14339ce1720bba2e75d7b6f8f712440" } } ], "extra": [ 1, 110, 232, 167, 22, 205, 7, 83, 60, 188, 60, 204, 103, 211, 14, 88, 90, 52, 140, 245, 76, 127, 57, 91, 216, 60, 138, 160, 197, 162, 230, 95, 6, 2, 17, 0, 0, 0, 3, 112, 96, 157, 3, 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