Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a202bfda9c7938b6bcf50aa14b2cff3451cd559db95dddd4277c1d3833a17a9

Tx prefix hash: f87139bc2823278192826bbfb6c40d7ea2f3b4bb1a03ee8c10caf113f928c40f
Tx public key: f7f8a54adc51a4347d9464ecce4c164254864600ab4deab42c3e5c688036f889
Timestamp: 1703318410 Timestamp [UCT]: 2023-12-23 08:00:10 Age [y:d:h:m:s]: 01:147:11:37:21
Block: 919254 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366553 RingCT/type: yes/0
Extra: 01f7f8a54adc51a4347d9464ecce4c164254864600ab4deab42c3e5c688036f8890211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c0c05ea0cbdb405c88dac66149e894d69d729fa155eb7c985a9baabd21c0dc4 0.600000000000 1376920 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": 919264, "vin": [ { "gen": { "height": 919254 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c0c05ea0cbdb405c88dac66149e894d69d729fa155eb7c985a9baabd21c0dc4" } } ], "extra": [ 1, 247, 248, 165, 74, 220, 81, 164, 52, 125, 148, 100, 236, 206, 76, 22, 66, 84, 134, 70, 0, 171, 77, 234, 180, 44, 62, 92, 104, 128, 54, 248, 137, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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