Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f24c1bbd8accf6af5df913dc91fd595dc55179d1504833750c4ea59b787336b

Tx prefix hash: 63931105646a0da878fb53ca61e335bbab6cc9cdb96bd572867615373833944b
Tx public key: 0d3803a41aa823bd7b10b00592a4331eaa026b733def5e9857fabeb6157ec1c6
Timestamp: 1719281831 Timestamp [UCT]: 2024-06-25 02:17:11 Age [y:d:h:m:s]: 00:281:04:06:38
Block: 1051592 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200908 RingCT/type: yes/0
Extra: 010d3803a41aa823bd7b10b00592a4331eaa026b733def5e9857fabeb6157ec1c60211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dac2034f3d5dbd51f144c5056c719c594e0dc32891a2e123451cee3150cb5d29 0.600000000000 1521907 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": 1051602, "vin": [ { "gen": { "height": 1051592 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dac2034f3d5dbd51f144c5056c719c594e0dc32891a2e123451cee3150cb5d29" } } ], "extra": [ 1, 13, 56, 3, 164, 26, 168, 35, 189, 123, 16, 176, 5, 146, 164, 51, 30, 170, 2, 107, 115, 61, 239, 94, 152, 87, 250, 190, 182, 21, 126, 193, 198, 2, 17, 0, 0, 0, 1, 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