Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 471697ac917b966dff0d0f0dd9f2708b6fd65c577495ca1a672a2291cf5fde1d

Tx prefix hash: 864372f4b5ec32fa4ca896350303635d9f1525b9cd2a8a67bf537caeaf6deee6
Tx public key: c4d979c7536cf5a23018e8f4de215586fbef14f0c9f62e0a1209e56d4ba42f29
Timestamp: 1646381246 Timestamp [UCT]: 2022-03-04 08:07:26 Age [y:d:h:m:s]: 03:242:08:03:34
Block: 451058 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 950987 RingCT/type: yes/0
Extra: 01c4d979c7536cf5a23018e8f4de215586fbef14f0c9f62e0a1209e56d4ba42f29021100000004cb8520c2000000000000000000

1 output(s) for total of 19.654313548000 dcy

stealth address amount amount idx
00: 3af5fef8704a689c5fb6c511f307d2f56e9dd37c249b2d23c2c71f9b4c3ec2f1 19.654313548000 866025 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": 451068, "vin": [ { "gen": { "height": 451058 } } ], "vout": [ { "amount": 19654313548, "target": { "key": "3af5fef8704a689c5fb6c511f307d2f56e9dd37c249b2d23c2c71f9b4c3ec2f1" } } ], "extra": [ 1, 196, 217, 121, 199, 83, 108, 245, 162, 48, 24, 232, 244, 222, 33, 85, 134, 251, 239, 20, 240, 201, 246, 46, 10, 18, 9, 229, 109, 75, 164, 47, 41, 2, 17, 0, 0, 0, 4, 203, 133, 32, 194, 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