Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0ec1c8463f60f378880935b1b31e3a8c52b28696183072f70deb9e77cade78e

Tx prefix hash: 65cf99d654725500b8b7877e7db10f5be479bd743419e0589b207b4f1aa5c485
Tx public key: e84f975d3620ad68db182eaa0f6be096548e8cf6994bae8262a49c428d2ff0f3
Timestamp: 1732113621 Timestamp [UCT]: 2024-11-20 14:40:21 Age [y:d:h:m:s]: 00:137:07:30:51
Block: 1157886 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97943 RingCT/type: yes/0
Extra: 01e84f975d3620ad68db182eaa0f6be096548e8cf6994bae8262a49c428d2ff0f30211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d3cd866f83ca42ac7a5252bd86434f61ba7d65c2783c94d7e75439c5873534d 0.600000000000 1643509 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": 1157896, "vin": [ { "gen": { "height": 1157886 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d3cd866f83ca42ac7a5252bd86434f61ba7d65c2783c94d7e75439c5873534d" } } ], "extra": [ 1, 232, 79, 151, 93, 54, 32, 173, 104, 219, 24, 46, 170, 15, 107, 224, 150, 84, 142, 140, 246, 153, 75, 174, 130, 98, 164, 156, 66, 141, 47, 240, 243, 2, 17, 0, 0, 0, 3, 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