Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e94835780e0a444161de1b1635d707fbb36c8bf7119b5ff637d43f7b60599d95

Tx prefix hash: 6535231bebcb267247dd21b0c48aeccaec2e2ea2f2b12d793b69c18b561f492e
Tx public key: 38b07423caf28e51255061846fbc794b3e75af7131f0df07291a8d0174d80b2a
Timestamp: 1703280877 Timestamp [UCT]: 2023-12-22 21:34:37 Age [y:d:h:m:s]: 01:153:15:49:03
Block: 918943 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370978 RingCT/type: yes/0
Extra: 0138b07423caf28e51255061846fbc794b3e75af7131f0df07291a8d0174d80b2a02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e7d6ff7189e8552960d72b62de0e73df167a0a4270a817926b4f6ad95d8c1b6 0.600000000000 1376607 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": 918953, "vin": [ { "gen": { "height": 918943 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e7d6ff7189e8552960d72b62de0e73df167a0a4270a817926b4f6ad95d8c1b6" } } ], "extra": [ 1, 56, 176, 116, 35, 202, 242, 142, 81, 37, 80, 97, 132, 111, 188, 121, 75, 62, 117, 175, 113, 49, 240, 223, 7, 41, 26, 141, 1, 116, 216, 11, 42, 2, 17, 0, 0, 0, 1, 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