Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85a1ab50619ee8506892a2fc5e11b2706b0576505990114f6a99614d711e59bf

Tx prefix hash: 65cc27b729aea5a5eed938c25b29c57870877751cdfd3319e6318a4714375c25
Tx public key: 40eae595f85ec357923e5a1300e5d9900480054e23ca9f4c2f0882982b06f2ae
Timestamp: 1707585592 Timestamp [UCT]: 2024-02-10 17:19:52 Age [y:d:h:m:s]: 01:060:08:32:44
Block: 954627 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304188 RingCT/type: yes/0
Extra: 0140eae595f85ec357923e5a1300e5d9900480054e23ca9f4c2f0882982b06f2ae02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 341cd0710d9a59c520d5e5cd76b0ab498c91d9cf18ae0e3b0d642c6ff5705e1f 0.600000000000 1413907 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": 954637, "vin": [ { "gen": { "height": 954627 } } ], "vout": [ { "amount": 600000000, "target": { "key": "341cd0710d9a59c520d5e5cd76b0ab498c91d9cf18ae0e3b0d642c6ff5705e1f" } } ], "extra": [ 1, 64, 234, 229, 149, 248, 94, 195, 87, 146, 62, 90, 19, 0, 229, 217, 144, 4, 128, 5, 78, 35, 202, 159, 76, 47, 8, 130, 152, 43, 6, 242, 174, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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