Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1d19c57b6c5102a56ab32f02c327e19f4494650f61a678f849d40c5d6938c5e

Tx prefix hash: 10532249eb5fcb366fc6ae921bd03e119e3d45a70ec28ee8695c0f0fde39f551
Tx public key: 8814a9f497ee18a2d1257e1c1b8efd41f39c363a2d47cdeed87b1b512ef39c65
Timestamp: 1720042944 Timestamp [UCT]: 2024-07-03 21:42:24 Age [y:d:h:m:s]: 00:282:21:46:24
Block: 1057908 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202147 RingCT/type: yes/0
Extra: 018814a9f497ee18a2d1257e1c1b8efd41f39c363a2d47cdeed87b1b512ef39c650211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e51f119e6a13686eca57aed0544555056a9ab2853fedf6a06f282d2e46eaab0 0.600000000000 1528351 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": 1057918, "vin": [ { "gen": { "height": 1057908 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e51f119e6a13686eca57aed0544555056a9ab2853fedf6a06f282d2e46eaab0" } } ], "extra": [ 1, 136, 20, 169, 244, 151, 238, 24, 162, 209, 37, 126, 28, 27, 142, 253, 65, 243, 156, 54, 58, 45, 71, 205, 238, 216, 123, 27, 81, 46, 243, 156, 101, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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