Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a1e2207544aa8672efa95cc92fd677d72a7a6d989d5f48b55b3d91eaec1dfef

Tx prefix hash: 72f03482d896dee2aaa26479764cb18289cc5df2709dcd5bc099733498380935
Tx public key: 0cfb714abfdf6571669dd695b514ccb70c9c543614e1fbfae799646ea84343f2
Timestamp: 1751792471 Timestamp [UCT]: 2025-07-06 09:01:11 Age [y:d:h:m:s]: 00:143:07:22:34
Block: 1319829 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100831 RingCT/type: yes/0
Extra: 010cfb714abfdf6571669dd695b514ccb70c9c543614e1fbfae799646ea84343f2021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d004050eb4a2f2bdb500d57cae2d33f190b01efd1a5d21e26356d7b8752c6dd8 0.600000000000 1807522 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": 1319839, "vin": [ { "gen": { "height": 1319829 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d004050eb4a2f2bdb500d57cae2d33f190b01efd1a5d21e26356d7b8752c6dd8" } } ], "extra": [ 1, 12, 251, 113, 74, 191, 223, 101, 113, 102, 157, 214, 149, 181, 20, 204, 183, 12, 156, 84, 54, 20, 225, 251, 250, 231, 153, 100, 110, 168, 67, 67, 242, 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