Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da11bb94c3939e47d8202e51637c8686414a3e378e2aa77fed9ee830c39a7282

Tx prefix hash: d1dbfa0c5f04816fc7e57236f9855b6a57e9cf9b8dfc868e582e5a08847dc049
Tx public key: c04ab56bf144efaa877c24ad13b4af14e1f98814dc4586ca6f1969f58ee0a7e5
Timestamp: 1726560904 Timestamp [UCT]: 2024-09-17 08:15:04 Age [y:d:h:m:s]: 00:178:10:55:29
Block: 1111951 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127373 RingCT/type: yes/0
Extra: 01c04ab56bf144efaa877c24ad13b4af14e1f98814dc4586ca6f1969f58ee0a7e502110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb37657d7e64e60b23e65dc1ad0be1e9e72d59cec183eeb4fddbf5c759bc91f1 0.600000000000 1591092 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": 1111961, "vin": [ { "gen": { "height": 1111951 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb37657d7e64e60b23e65dc1ad0be1e9e72d59cec183eeb4fddbf5c759bc91f1" } } ], "extra": [ 1, 192, 74, 181, 107, 241, 68, 239, 170, 135, 124, 36, 173, 19, 180, 175, 20, 225, 249, 136, 20, 220, 69, 134, 202, 111, 25, 105, 245, 142, 224, 167, 229, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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