Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71c899d54a9bd67e2388678937f1cc37d3a6f5ca6ea13cc6801fb94ba487f6e5

Tx prefix hash: f599e242464d12ba7edec2fccc0fbc61d21b30211ab6c084d93ccdb69a9cb000
Tx public key: beb6d6b9bb0ee28d0049fdf8a377638a80332957dddb3d381fab1aeadafd09e0
Timestamp: 1752549781 Timestamp [UCT]: 2025-07-15 03:23:01 Age [y:d:h:m:s]: 00:177:14:26:55
Block: 1325749 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125745 RingCT/type: yes/0
Extra: 01beb6d6b9bb0ee28d0049fdf8a377638a80332957dddb3d381fab1aeadafd09e002110000000643846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac4c4e139a9c8d551758220e6833db53f3864252b419a9f836a2fd81cc86c312 0.600000000000 1813496 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": 1325759, "vin": [ { "gen": { "height": 1325749 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac4c4e139a9c8d551758220e6833db53f3864252b419a9f836a2fd81cc86c312" } } ], "extra": [ 1, 190, 182, 214, 185, 187, 14, 226, 141, 0, 73, 253, 248, 163, 119, 99, 138, 128, 51, 41, 87, 221, 219, 61, 56, 31, 171, 26, 234, 218, 253, 9, 224, 2, 17, 0, 0, 0, 6, 67, 132, 109, 102, 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