Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3002c1d4f33f147789da19e64f7e5a87ed5dc518f157a710995d75d2f597545a

Tx prefix hash: 686aebd0f8d144f3b46cf9d7c307a8d0d1bc09b69e12be7e2b3acead455b5afc
Tx public key: b127e52737fdbaf5ce4a83e233a29b1b948ea7ff38fdc96fb2476e7d256bb2de
Timestamp: 1750712697 Timestamp [UCT]: 2025-06-23 21:04:57 Age [y:d:h:m:s]: 00:149:20:39:28
Block: 1311354 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105035 RingCT/type: yes/0
Extra: 01b127e52737fdbaf5ce4a83e233a29b1b948ea7ff38fdc96fb2476e7d256bb2de02110000000743846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72e1260a035631260b8fc59a814b81acfb38fae9c5b6db56b3cc00d77d7a8d11 0.600000000000 1798981 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": 1311364, "vin": [ { "gen": { "height": 1311354 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72e1260a035631260b8fc59a814b81acfb38fae9c5b6db56b3cc00d77d7a8d11" } } ], "extra": [ 1, 177, 39, 229, 39, 55, 253, 186, 245, 206, 74, 131, 226, 51, 162, 155, 27, 148, 142, 167, 255, 56, 253, 201, 111, 178, 71, 110, 125, 37, 107, 178, 222, 2, 17, 0, 0, 0, 7, 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