Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e9a9b0c98b2baea0503bb91e2590fd130553448c8e5fd6b7c7daed30aba18da

Tx prefix hash: 687fe643e5f7a4c04c98e225f2b41b699fdb01cddbd0243c7e203ce60da3b3a6
Tx public key: 51540e87f97a795e0db46a0de18a10916f7bb12a638592d06893124e7743c2f1
Timestamp: 1759000629 Timestamp [UCT]: 2025-09-27 19:17:09 Age [y:d:h:m:s]: 00:010:14:56:51
Block: 1377770 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7596 RingCT/type: yes/0
Extra: 0151540e87f97a795e0db46a0de18a10916f7bb12a638592d06893124e7743c2f1021100000003a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da4ce4284ecaa4a18a2bb81ea2b40b993b18a064a83dcc1224e23bc23351b9c6 0.600000000000 1865865 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": 1377780, "vin": [ { "gen": { "height": 1377770 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da4ce4284ecaa4a18a2bb81ea2b40b993b18a064a83dcc1224e23bc23351b9c6" } } ], "extra": [ 1, 81, 84, 14, 135, 249, 122, 121, 94, 13, 180, 106, 13, 225, 138, 16, 145, 111, 123, 177, 42, 99, 133, 146, 208, 104, 147, 18, 78, 119, 67, 194, 241, 2, 17, 0, 0, 0, 3, 165, 220, 205, 121, 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