Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a464bd3e50328a2199c69e02fe36684ebe38c2a1a8e6e911ff20cbd7580e2744

Tx prefix hash: 7181cf72bf1e5335d3d8dcd939444160a35ecb9e54fd987a7ae6ef248d24d84e
Tx public key: fcef8e85ad12cbb64bbf77a6b7af7f67cfd1d46f5538a144c300ac89020913d3
Timestamp: 1754020154 Timestamp [UCT]: 2025-08-01 03:49:14 Age [y:d:h:m:s]: 00:068:15:17:53
Block: 1337773 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 47871 RingCT/type: yes/0
Extra: 01fcef8e85ad12cbb64bbf77a6b7af7f67cfd1d46f5538a144c300ac89020913d3021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f1f4b38fa1bbe537797d21e61372c3f09b5937be925348b8656f589d46ef8a9 0.600000000000 1825578 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": 1337783, "vin": [ { "gen": { "height": 1337773 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f1f4b38fa1bbe537797d21e61372c3f09b5937be925348b8656f589d46ef8a9" } } ], "extra": [ 1, 252, 239, 142, 133, 173, 18, 203, 182, 75, 191, 119, 166, 183, 175, 127, 103, 207, 209, 212, 111, 85, 56, 161, 68, 195, 0, 172, 137, 2, 9, 19, 211, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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