Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a205333b7fe92e923fba80ae64fa30e3fb17fefaaf1163893532a236d6bcde01

Tx prefix hash: d2bc5e93a0c0d7ae4809048e1dc2d2e96fcec3853e59e8e22badf14fe78d74b4
Tx public key: c66b0e19f0030f00e206204dcccff89496d3dac27ef0d5267bf5ea5b9ca83241
Timestamp: 1720073909 Timestamp [UCT]: 2024-07-04 06:18:29 Age [y:d:h:m:s]: 00:273:14:05:38
Block: 1058166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195473 RingCT/type: yes/0
Extra: 01c66b0e19f0030f00e206204dcccff89496d3dac27ef0d5267bf5ea5b9ca8324102110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a0c070ba9fc4caf57524f4d92dbddcc32e131a3c6c35ea7bff9c95155479bea 0.600000000000 1528615 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": 1058176, "vin": [ { "gen": { "height": 1058166 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a0c070ba9fc4caf57524f4d92dbddcc32e131a3c6c35ea7bff9c95155479bea" } } ], "extra": [ 1, 198, 107, 14, 25, 240, 3, 15, 0, 226, 6, 32, 77, 204, 207, 248, 148, 150, 211, 218, 194, 126, 240, 213, 38, 123, 245, 234, 91, 156, 168, 50, 65, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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