Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5cfe21eb85945cc61bd9902e8313c1fcc24a7ddb2e8f5e2bdeae7badb8dbdf0

Tx prefix hash: 6721c91c9e1c71939c9f627e2db062b9df539cf7df0662bc9627185dffd384e3
Tx public key: 50eaaafd527f517a2089ee659cf0d1c12c63ece82a52bc8355a91bed776710fb
Timestamp: 1725359316 Timestamp [UCT]: 2024-09-03 10:28:36 Age [y:d:h:m:s]: 00:117:06:38:18
Block: 1101993 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83870 RingCT/type: yes/0
Extra: 0150eaaafd527f517a2089ee659cf0d1c12c63ece82a52bc8355a91bed776710fb021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b73770e60d0ebdff8dfe3bb58363429ffe6432dc3a02e76b29719299e3df253 0.600000000000 1578256 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": 1102003, "vin": [ { "gen": { "height": 1101993 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b73770e60d0ebdff8dfe3bb58363429ffe6432dc3a02e76b29719299e3df253" } } ], "extra": [ 1, 80, 234, 170, 253, 82, 127, 81, 122, 32, 137, 238, 101, 156, 240, 209, 193, 44, 99, 236, 232, 42, 82, 188, 131, 85, 169, 27, 237, 119, 103, 16, 251, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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