Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20c96da3176f7bcedc03986e5487bf31e42aae89c964d9974f1fbb5973b3c06e

Tx prefix hash: f2b3bbae16a3b7c2fde1c22fc931801e497477e1ecba8cd879b8c15a6fe5aa53
Tx public key: 38c49940a3224f58323638c0465dd22442777a276ce6db145bd7895be069a8d6
Timestamp: 1696070441 Timestamp [UCT]: 2023-09-30 10:40:41 Age [y:d:h:m:s]: 01:200:11:23:14
Block: 859375 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 404321 RingCT/type: yes/0
Extra: 0138c49940a3224f58323638c0465dd22442777a276ce6db145bd7895be069a8d60211000000014b8f5122000000000000000000

1 output(s) for total of 0.872035017000 dcy

stealth address amount amount idx
00: 4ee2c647991f6f4847f16fea044bec7178e0a35253f2ebf7e4403a319d728833 0.872035017000 1313599 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": 859385, "vin": [ { "gen": { "height": 859375 } } ], "vout": [ { "amount": 872035017, "target": { "key": "4ee2c647991f6f4847f16fea044bec7178e0a35253f2ebf7e4403a319d728833" } } ], "extra": [ 1, 56, 196, 153, 64, 163, 34, 79, 88, 50, 54, 56, 192, 70, 93, 210, 36, 66, 119, 122, 39, 108, 230, 219, 20, 91, 215, 137, 91, 224, 105, 168, 214, 2, 17, 0, 0, 0, 1, 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