Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6ef7f8102893d2e45bf976fd4945a5fce5bbf8811552e4f1b85dcb482919cfd

Tx prefix hash: fa5782560b264574b4e8ccc628361b7c78ff3081cb4f18be927d8aa6456ab642
Tx public key: 86704e92bf463ec81dfada7998ce8f93d1d49d79322fb1e09ebbfd7957ca98a8
Timestamp: 1708713560 Timestamp [UCT]: 2024-02-23 18:39:20 Age [y:d:h:m:s]: 01:045:10:55:11
Block: 963986 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293500 RingCT/type: yes/0
Extra: 0186704e92bf463ec81dfada7998ce8f93d1d49d79322fb1e09ebbfd7957ca98a802110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a1fae7d28bdacd33e77b6a020131b4a6bbbbb23be853b8da9ae7ee203da37b3 0.600000000000 1423713 of 15

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": 963996, "vin": [ { "gen": { "height": 963986 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a1fae7d28bdacd33e77b6a020131b4a6bbbbb23be853b8da9ae7ee203da37b3" } } ], "extra": [ 1, 134, 112, 78, 146, 191, 70, 62, 200, 29, 250, 218, 121, 152, 206, 143, 147, 209, 212, 157, 121, 50, 47, 177, 224, 158, 187, 253, 121, 87, 202, 152, 168, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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