Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65564b23f563bdc63c6a807a3d6f5a6c29bc0e50b390333678954a3d69a7bd54

Tx prefix hash: a47b8fd24c55287d796fea08f16469d083cded3cf6b53f9a281f378ed427fc42
Tx public key: c046cdc0791e2a4585c5f2980c78996712ee8fb665729afa0f17d467629aca79
Timestamp: 1636931829 Timestamp [UCT]: 2021-11-14 23:17:09 Age [y:d:h:m:s]: 03:120:16:28:28
Block: 374431 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 864792 RingCT/type: yes/0
Extra: 01c046cdc0791e2a4585c5f2980c78996712ee8fb665729afa0f17d467629aca790211000000124a0f5013000000000000000000

1 output(s) for total of 35.265906448000 dcy

stealth address amount amount idx
00: 6dc5de666b9a12c7f14a2175f747494266caac845105a30c43ce99e21aadbc79 35.265906448000 757901 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": 374441, "vin": [ { "gen": { "height": 374431 } } ], "vout": [ { "amount": 35265906448, "target": { "key": "6dc5de666b9a12c7f14a2175f747494266caac845105a30c43ce99e21aadbc79" } } ], "extra": [ 1, 192, 70, 205, 192, 121, 30, 42, 69, 133, 197, 242, 152, 12, 120, 153, 103, 18, 238, 143, 182, 101, 114, 154, 250, 15, 23, 212, 103, 98, 154, 202, 121, 2, 17, 0, 0, 0, 18, 74, 15, 80, 19, 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