Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 021fbf0ca0a35f5314943829d856043f727a8060af9dd15a2ca1fa1beade2c11

Tx prefix hash: ce300ca9e8b084f85643831f36c517ed07ea186474be4574e690c5ed5c37af62
Tx public key: eedd42c1053aa6c610ce5c3f8b405011d22ced6fe84293a9847add0acff03db8
Timestamp: 1725075943 Timestamp [UCT]: 2024-08-31 03:45:43 Age [y:d:h:m:s]: 00:152:17:51:40
Block: 1099636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108992 RingCT/type: yes/0
Extra: 01eedd42c1053aa6c610ce5c3f8b405011d22ced6fe84293a9847add0acff03db802110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 81aa3e190dd014a451f587d227d48a3ddd94afe8d01cb4d0b7efd40200dd1110 0.600000000000 1575601 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": 1099646, "vin": [ { "gen": { "height": 1099636 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81aa3e190dd014a451f587d227d48a3ddd94afe8d01cb4d0b7efd40200dd1110" } } ], "extra": [ 1, 238, 221, 66, 193, 5, 58, 166, 198, 16, 206, 92, 63, 139, 64, 80, 17, 210, 44, 237, 111, 232, 66, 147, 169, 132, 122, 221, 10, 207, 240, 61, 184, 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