Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 688a393819bd326b9197fe223ca16d0a6e34e1e3a685e8289b9988b0a9556928

Tx prefix hash: 58e257ee413f5f93f54d4c70df9688252488b45a1875abaecd585e694e7e029c
Tx public key: d04fd08e59631a71916102a62d7f963cf5d9631e513aa625f05619333de4fd18
Timestamp: 1755222591 Timestamp [UCT]: 2025-08-15 01:49:51 Age [y:d:h:m:s]: 00:096:12:18:42
Block: 1346929 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68642 RingCT/type: yes/0
Extra: 01d04fd08e59631a71916102a62d7f963cf5d9631e513aa625f05619333de4fd1802110000000601491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f35a941601864472447f467407f55fae28760e4c3fee05b81c02db42e01ade64 0.600000000000 1834838 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": 1346939, "vin": [ { "gen": { "height": 1346929 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f35a941601864472447f467407f55fae28760e4c3fee05b81c02db42e01ade64" } } ], "extra": [ 1, 208, 79, 208, 142, 89, 99, 26, 113, 145, 97, 2, 166, 45, 127, 150, 60, 245, 217, 99, 30, 81, 58, 166, 37, 240, 86, 25, 51, 61, 228, 253, 24, 2, 17, 0, 0, 0, 6, 1, 73, 31, 136, 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