Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3501837c3313d549dc4579f5710df72cc6be670d5a0c99522865470b46b5b15f

Tx prefix hash: 3c64fefb743d616e295c139c2f7fd526f02a9d5fbc6557fd13e0a4e0696d1e6f
Tx public key: 984f121f800140e504128ea0f919a8ca2652a51706dd2a3532ae4861a4a57a7d
Timestamp: 1581320689 Timestamp [UCT]: 2020-02-10 07:44:49 Age [y:d:h:m:s]: 04:357:15:06:15
Block: 61785 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1147588 RingCT/type: yes/0
Extra: 01984f121f800140e504128ea0f919a8ca2652a51706dd2a3532ae4861a4a57a7d02110000000d4ac5aa02000000000000000000

1 output(s) for total of 383.072929176000 dcy

stealth address amount amount idx
00: 037036d16cb7869d3677089ac29630f5dca747f1a313ccc279d6cbd8221ea514 383.072929176000 113948 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": 61795, "vin": [ { "gen": { "height": 61785 } } ], "vout": [ { "amount": 383072929176, "target": { "key": "037036d16cb7869d3677089ac29630f5dca747f1a313ccc279d6cbd8221ea514" } } ], "extra": [ 1, 152, 79, 18, 31, 128, 1, 64, 229, 4, 18, 142, 160, 249, 25, 168, 202, 38, 82, 165, 23, 6, 221, 42, 53, 50, 174, 72, 97, 164, 165, 122, 125, 2, 17, 0, 0, 0, 13, 74, 197, 170, 2, 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