Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 638d40bd4d8a73add8095a5f4e3a9c9863298d15530482c5283cf1ab102dee3d

Tx prefix hash: 1aaca4b6d586661ac5cbd050d9f3f9ba4fa4c74c00a68484d0bbb9635f22ba41
Tx public key: bdf95352b72c140a8eef1f9998ceb5cc9b098a43a6c31a3265d2cf4c1f916a88
Timestamp: 1716233977 Timestamp [UCT]: 2024-05-20 19:39:37 Age [y:d:h:m:s]: 00:235:10:43:06
Block: 1026337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168516 RingCT/type: yes/0
Extra: 01bdf95352b72c140a8eef1f9998ceb5cc9b098a43a6c31a3265d2cf4c1f916a8802110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a6e10873157a09f19400c98ddd5eecd5084d9238b1b2e4c1ddfabefa8b8ea38 0.600000000000 1493364 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": 1026347, "vin": [ { "gen": { "height": 1026337 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a6e10873157a09f19400c98ddd5eecd5084d9238b1b2e4c1ddfabefa8b8ea38" } } ], "extra": [ 1, 189, 249, 83, 82, 183, 44, 20, 10, 142, 239, 31, 153, 152, 206, 181, 204, 155, 9, 138, 67, 166, 195, 26, 50, 101, 210, 207, 76, 31, 145, 106, 136, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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