Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2002d2bad815d24eded01e140d88b056527cac0b16105817c21f64f484d722af

Tx prefix hash: 0cf8b74229f646b9d097c7b5084484f78d6ec274aa650d3c70877ab6c043a38f
Tx public key: 6f10836f4e869b3ae04bf87fdc957dc45415eed52f9b75c86b12cb57b93a74db
Timestamp: 1701611805 Timestamp [UCT]: 2023-12-03 13:56:45 Age [y:d:h:m:s]: 01:178:18:38:35
Block: 905102 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388976 RingCT/type: yes/0
Extra: 016f10836f4e869b3ae04bf87fdc957dc45415eed52f9b75c86b12cb57b93a74db021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.615207079000 dcy

stealth address amount amount idx
00: 7317b9717320f7b64f7774e9332590a809d668ad4d9984bfedb78152a293adf0 0.615207079000 1361973 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": 905112, "vin": [ { "gen": { "height": 905102 } } ], "vout": [ { "amount": 615207079, "target": { "key": "7317b9717320f7b64f7774e9332590a809d668ad4d9984bfedb78152a293adf0" } } ], "extra": [ 1, 111, 16, 131, 111, 78, 134, 155, 58, 224, 75, 248, 127, 220, 149, 125, 196, 84, 21, 238, 213, 47, 155, 117, 200, 107, 18, 203, 87, 185, 58, 116, 219, 2, 17, 0, 0, 0, 7, 230, 210, 127, 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