Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 355bb2ad42f9b5a1ffb97f3c4931669aca34ba818c3c81ed37276e66b6404bea

Tx prefix hash: f0f81b2db77aad1a59392ef893e79332bba3f5510ca3fa975818eb2f3503798b
Tx public key: c54835809751b7a9d1d0540cdcbf7f5ca6f012568c14fb910a180bb844a8d321
Timestamp: 1765674886 Timestamp [UCT]: 2025-12-14 01:14:46 Age [y:d:h:m:s]: 00:009:09:24:21
Block: 1433078 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6720 RingCT/type: yes/0
Extra: 01c54835809751b7a9d1d0540cdcbf7f5ca6f012568c14fb910a180bb844a8d321021100000001d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb9a658abbeff1ff90b5f692f33a4c524b72b1e8dfdf29caaed2108e6d60a4d3 0.600000000000 1921857 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": 1433088, "vin": [ { "gen": { "height": 1433078 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb9a658abbeff1ff90b5f692f33a4c524b72b1e8dfdf29caaed2108e6d60a4d3" } } ], "extra": [ 1, 197, 72, 53, 128, 151, 81, 183, 169, 209, 208, 84, 12, 220, 191, 127, 92, 166, 240, 18, 86, 140, 20, 251, 145, 10, 24, 11, 184, 68, 168, 211, 33, 2, 17, 0, 0, 0, 1, 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