Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f77545cbce3e9b6aa1cbbd65c35a40ed68fd1204f8995c919e9ff072b58b1a6

Tx prefix hash: 085ca9565c818ca51d4e6f5750c4689a7fb3fd09fc615334487be75bdead151b
Tx public key: c780c3787671fe35eb30d637a132d1313dd2d6edd7552a6f5e1cc975aa45b878
Timestamp: 1685143139 Timestamp [UCT]: 2023-05-26 23:18:59 Age [y:d:h:m:s]: 01:313:07:36:46
Block: 768828 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 485133 RingCT/type: yes/0
Extra: 01c780c3787671fe35eb30d637a132d1313dd2d6edd7552a6f5e1cc975aa45b878021100000002b3164c24000000000000000000

1 output(s) for total of 1.740018460000 dcy

stealth address amount amount idx
00: 30da39daec0275925a0bdf5dd0c7c3443d6f31b63d7e2357de9018a28b698f87 1.740018460000 1218043 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": 768838, "vin": [ { "gen": { "height": 768828 } } ], "vout": [ { "amount": 1740018460, "target": { "key": "30da39daec0275925a0bdf5dd0c7c3443d6f31b63d7e2357de9018a28b698f87" } } ], "extra": [ 1, 199, 128, 195, 120, 118, 113, 254, 53, 235, 48, 214, 55, 161, 50, 209, 49, 61, 210, 214, 237, 215, 85, 42, 111, 94, 28, 201, 117, 170, 69, 184, 120, 2, 17, 0, 0, 0, 2, 179, 22, 76, 36, 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