Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a86d7be4b6be2530b05456f0f755a41f610c322325aa0a318834966147121c7a

Tx prefix hash: e101e2b8a5ca8e69059d20bd0d472c3bf537a6d4a40e709b70db6bc7851e1b85
Tx public key: bc6a347be4401fff427d4c8815e86ce70352d28f48801dae4eaaa57532141076
Timestamp: 1686526792 Timestamp [UCT]: 2023-06-11 23:39:52 Age [y:d:h:m:s]: 02:194:00:03:50
Block: 780305 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 658467 RingCT/type: yes/0
Extra: 01bc6a347be4401fff427d4c8815e86ce70352d28f48801dae4eaaa57532141076021100000002272bcc39000000000000000000

1 output(s) for total of 1.594137484000 dcy

stealth address amount amount idx
00: d2986961a00e50d545f4b1004bf617b3b0c6aa59cb3c35cb9023f7d05235d612 1.594137484000 1230008 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": 780315, "vin": [ { "gen": { "height": 780305 } } ], "vout": [ { "amount": 1594137484, "target": { "key": "d2986961a00e50d545f4b1004bf617b3b0c6aa59cb3c35cb9023f7d05235d612" } } ], "extra": [ 1, 188, 106, 52, 123, 228, 64, 31, 255, 66, 125, 76, 136, 21, 232, 108, 231, 3, 82, 210, 143, 72, 128, 29, 174, 78, 170, 165, 117, 50, 20, 16, 118, 2, 17, 0, 0, 0, 2, 39, 43, 204, 57, 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