Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d69c397bc00b92c0dd1720a07e698651a9c67525b9d37f7b8da628d8fcc068e3

Tx prefix hash: cde9e279194a6c2070e942c7e4257dc1eb5f24e2ec2252f5ad82e3e06e616090
Tx public key: 6c2aa41369fb8197f859ed0c66d1842a51fddcf2bd7600968b9037827e70fa72
Timestamp: 1697365516 Timestamp [UCT]: 2023-10-15 10:25:16 Age [y:d:h:m:s]: 01:246:08:45:26
Block: 870107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 437040 RingCT/type: yes/0
Extra: 016c2aa41369fb8197f859ed0c66d1842a51fddcf2bd7600968b9037827e70fa72021100000017faf35c9c000000000000000000

1 output(s) for total of 0.803478643000 dcy

stealth address amount amount idx
00: 1c8e2c385861bb4023f766dd46058a5687ebec172c93d9f9bf0891fed40337fa 0.803478643000 1324980 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": 870117, "vin": [ { "gen": { "height": 870107 } } ], "vout": [ { "amount": 803478643, "target": { "key": "1c8e2c385861bb4023f766dd46058a5687ebec172c93d9f9bf0891fed40337fa" } } ], "extra": [ 1, 108, 42, 164, 19, 105, 251, 129, 151, 248, 89, 237, 12, 102, 209, 132, 42, 81, 253, 220, 242, 189, 118, 0, 150, 139, 144, 55, 130, 126, 112, 250, 114, 2, 17, 0, 0, 0, 23, 250, 243, 92, 156, 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