Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05ba34fc96fc567f602075a01c4e65fba87fbb38d2a9b1e1fde6366ec1245410

Tx prefix hash: 07818ce6c038adba4f14b80b6ab2b5244d9e8c7cc610a407ef23fc828ba38abf
Tx public key: 895297a7e5aee6188021f402725f20df197fbe2929672dce738ea0ae5d1d2fd9
Timestamp: 1735488888 Timestamp [UCT]: 2024-12-29 16:14:48 Age [y:d:h:m:s]: 00:116:15:09:46
Block: 1185830 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83171 RingCT/type: yes/0
Extra: 01895297a7e5aee6188021f402725f20df197fbe2929672dce738ea0ae5d1d2fd90211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c93afe9ffdf31da18181ccaa70917e99025e31744b64e5a13b72e50b82efafa9 0.600000000000 1672305 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": 1185840, "vin": [ { "gen": { "height": 1185830 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c93afe9ffdf31da18181ccaa70917e99025e31744b64e5a13b72e50b82efafa9" } } ], "extra": [ 1, 137, 82, 151, 167, 229, 174, 230, 24, 128, 33, 244, 2, 114, 95, 32, 223, 25, 127, 190, 41, 41, 103, 45, 206, 115, 142, 160, 174, 93, 29, 47, 217, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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