Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 692f0a5698d33ad9f30c655605c5be5dbb4196619bf6e1d4845dc9e86546103f

Tx prefix hash: 1f9868d7f03c5ba328b2274e4ac7de181f08bfc7699c2319325a8f4e74dcffb7
Tx public key: 6f48ff7e42ab9bc95efc1475671e8145f523e0654e418642726517c80cde96f9
Timestamp: 1716332819 Timestamp [UCT]: 2024-05-21 23:06:59 Age [y:d:h:m:s]: 00:302:01:27:44
Block: 1027154 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215908 RingCT/type: yes/0
Extra: 016f48ff7e42ab9bc95efc1475671e8145f523e0654e418642726517c80cde96f902110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d67d9f1c42407c64296544c0828a1f0c5540ecd8535e4adb449864c982d88dc 0.600000000000 1494629 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": 1027164, "vin": [ { "gen": { "height": 1027154 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d67d9f1c42407c64296544c0828a1f0c5540ecd8535e4adb449864c982d88dc" } } ], "extra": [ 1, 111, 72, 255, 126, 66, 171, 155, 201, 94, 252, 20, 117, 103, 30, 129, 69, 245, 35, 224, 101, 78, 65, 134, 66, 114, 101, 23, 200, 12, 222, 150, 249, 2, 17, 0, 0, 0, 6, 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