Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e58ca729854019df851508a95b98d7b4a4d218eed6b79dfc0006b8dfefa50655

Tx prefix hash: 8aec96dba74bb686a643a9c8ee420177587d8a86ba71b65a5eb7de4d858fcf56
Tx public key: 6d268c7663596fc558d641cbd6f730ea450f6c79d15cac7a738d42812b469f36
Timestamp: 1695586402 Timestamp [UCT]: 2023-09-24 20:13:22 Age [y:d:h:m:s]: 01:198:08:16:42
Block: 855349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 402827 RingCT/type: yes/0
Extra: 016d268c7663596fc558d641cbd6f730ea450f6c79d15cac7a738d42812b469f360211000000034b8f5122000000000000000000

1 output(s) for total of 0.899236113000 dcy

stealth address amount amount idx
00: a3c08696320426fa242c3f65b6b4f82304abe2bbd6d033dd0c216a338209953b 0.899236113000 1309367 of 0

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": 855359, "vin": [ { "gen": { "height": 855349 } } ], "vout": [ { "amount": 899236113, "target": { "key": "a3c08696320426fa242c3f65b6b4f82304abe2bbd6d033dd0c216a338209953b" } } ], "extra": [ 1, 109, 38, 140, 118, 99, 89, 111, 197, 88, 214, 65, 203, 214, 247, 48, 234, 69, 15, 108, 121, 209, 92, 172, 122, 115, 141, 66, 129, 43, 70, 159, 54, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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